updated template to address glibc build issues.

#48075 (comment)

Thanks for the reply. I feel as if there could've been more communicated as to why this branch was chosen over mortie's. The primary reason is that although you can build, it fails to launch. The reason being that sway has moved to a new input inhibitor protocol, and it is not supported by Mortie's fork of swaylock but is by Jirutka's. Here's some more information in a thread and by Mortie himself: mortie/swaylock-effects#112 (comment)

You can also see in that thread that people are recommending to install swaylock-effects-git, which is Jirutka's fork in the AUR. Although it's not being tended to much as well as Mortie's, I don't believe much has changed that requires being tended to. Such as a new input inhibitor protocol. https://aur.archlinux.org/packages/swaylock-effects-git

The primary benefit for myself is having the clock on the locked screen. Being able to tell the time at a glance without needing an externally powered device would be nice. I'm running out of wall outlets, and tired of buying batteries. Those things are expensive now!